Strip leading invalid characters from Schema (fix #489) #538
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previous one only leading matched digits
…_ |$), and when duplicate outputs
…isChong/json-schema-to-typescript into strip-leading-invalid-chars
|
Thanks for the contribution! Let's see if we can go with a more general approach here: #539. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed Issue #489
Updated function toSafeString in src/utils.ts to detect and remove all leading invalid characters.
Edit: Is relevant to issues #151 and #185
Would pre-empting invalid characters with an underscore to make them legal be more desirable?